Skip to main content

Redmine Projects

info

Redmine is an open-source project management tool that integrates multiple functionalities to support collaborative project planning and execution. This section will clarify key concepts and terminology in Redmine, providing a foundation for how it is used in our operations.

Core Concepts and Terminology​

  • Project: A project in Redmine is a broad container that organizes and tracks work. It can represent a large initiative or an ongoing area of work. For instance, Mission is our overarching project.

  • Sub-Project: Sub-projects are subdivisions within a project, used to manage specific areas or streams of work under the larger project umbrella. Examples include our Intel, Investigations, and W/S Support projects.

  • Issue: In Redmine, an issue is a fundamental entity used to track work, similar to a case or ticket in other systems. Each issue can represent a task, a bug, a feature request, or any other unit of work. Issues can be categorized, prioritized, assigned to specific team members, and tracked through their lifecycle from creation to closure.

  • Trackers: Trackers are a way to categorize issues within Redmine. They define the nature of an issue, like an incident, a task, a request, or notice. Each tracker can be configured with its custom workflow, ensuring that issues of different types follow appropriate steps from initiation to resolution.

262COS Redmine Projects​

Project Hierarchy

Mission Project​

  • Intent: Mission objectives and tasks should be created and assigned here for efficient mission management. In order to make full use of the built-in Gantt chart capability, the Start date, Due date, and % Done issue fields should populated appropriately.

    NOTE: Issues created/updated under this project will get auto-posted as a message to the Rocketchat accountability channel

    Example TO/TT gantt chart:

  • Issue Types:

    • Objective: Tactical Objective issue that usually a parent issue to Task issues fot Tactical Tasks that roll up under it.
    • Task: Tactical Task ticket to be explicitly assigned to individuals with a specified Start date/Due date.
    • Notice: A general notification ticket that acts as an informational post to all members that can be easily referenced.

Investigations Project​

  • Intent: Incident investigations should be tracked here for confirmed malicious or highly-suspect activities, unlike low-level alert investigation work like false positive clearing - which should remain closer to the tool of origin (such as Elastic Detection Alerts within Elastic Security Cases).

    NOTE: Issues created/updated under this project will get auto-posted as a message to the Rocketchat war_room channel

  • Issue Types:

    • Task: A specified tasking, such as performing a data collection or remediation action against a threat.
    • Incident: An incident tracking ticket that may be comprised of multiple related security events and alerts.

      Example Incident ticket:

Intel Project​

  • Intent: Intel related requests, such as RFIs (requests for information) and FFIRs (friendly forces information requests) should be created here for organized tracking and assignment.

    NOTE: Issues created/updated under this project will get auto-posted as a message to the Rocketchat intel channel

  • Issue Types:

    • Task: A specified tasking for completion of work - usually used for complex or long-term tasks.
    • Request: An intel related request, such as an RFI or FFIR.
    • Notice: A general notification ticket that acts as an informational post to all members that can be easily referenced.

W/S Support Project​

  • Intent: Major weapon system modification requests should be tracked here, especially for complex tasks or requests that require a highler level of coordination and cannot be as easily tracked via simple chat messages.

    NOTE: Issues created/updated under this project will get auto-posted as a message to the Rocketchat ws_support channel

  • Issue Types:

    • Task: A specified tasking for completion of work - usually used for complex or long-term tasks.
    • Request: A weapon system support related request, such as performing a unique DIP configuration.
    • Notice: A general notification ticket that acts as an informational post to all members that can be easily referenced.